Methods and apparatus to manage zones of a multi-zone media playback system

ABSTRACT

Methods and apparatus to manage zones of a multi-zone media playback system are disclosed. An example apparatus includes a user interface; a controller to configure one or more zone groups each associated with one or more media playback devices; a detector to monitor the user interface for a drag of an icon representative of a first one of the zone groups on the user interface from a first position to a second position; and a configuration implementer to change a configuration of the one or more zone groups in response to a detected drag of the icon.

CROSS-REFERENCE TO RELATED APPLICATION

This patent arises from a continuation of U.S. patent application Ser.No. 13/247,754, entitled “Methods and Apparatus to Manage Zones of aMulti-Zone Media Playback System,” filed on Sep. 28, 2011, now U.S. Pat.No. 9,052,810, which is hereby incorporated by reference for allpurposes.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer electronics and, moreparticularly, to methods and apparatus to manage zones of a multi-zonemedia playback system.

BACKGROUND

Technological advancements have increased the accessibility of musiccontent, as well as other types of media, such as television content,movies, and interactive content. For example, a user can access audio,video, or both audio and video content over the Internet through anonline store, an Internet radio station, an online music service, anonline movie service, and the like, in addition to the more traditionalavenues of accessing audio and video content. Demand for such audio andvideo content continues to surge. Given the high demand, technology usedto access and play such content has likewise improved.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologyare better understood with regard to the following description, appendedclaims, and accompanying drawings where:

FIG. 1 shows an illustration of an example system in which embodimentsof the methods and apparatus disclosed herein may be implemented;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and speakers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an internal functional block diagram of an exampleimplementation of the zone manager of FIG. 5;

FIG. 7 is a screenshot of an example user interface associated with theexample controller of FIG. 5;

FIG. 8 is a screenshot of an example zone panel of the example userinterface of FIG. 7;

FIG. 9 is a screenshot of an example zone panel of the example userinterface of FIG. 7;

FIG. 10 is a screenshot of an example zone panel of the example userinterface of FIG. 7;

FIG. 11 is a screenshot of an example zone panel of the example userinterface of FIG. 7;

FIG. 12 is a screenshot of an example zone panel of the example userinterface of FIG. 7;

FIG. 13 is a screenshot of an example zone panel of the example userinterface of FIG. 7;

FIG. 14 is a flow diagram representative of example machine readableinstructions that can be executed to implement the example zone managerof FIGS. 5 and/or 6;

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the present disclosure is notlimited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments of the methods and apparatus disclosed herein enable a userto easily and conveniently manage zones of a multi-zone media playbacksystem.

An example embodiment of an apparatus implemented in accordance with thepresent disclosure includes a user interface; a controller to configureone or more zone groups each associated with one or more media playbackdevices; a detector to monitor the user interface for a drag of an iconrepresentative of a first one of the zone groups on the user interfacefrom a first position to a second position; and a configurationimplementer to change a configuration of the one or more zone groups inresponse to a detected drag of the icon.

In some embodiments, the configuration implementer is to change theconfiguration of the one or more zone groups by, when the secondposition corresponds to a second one of the zone groups, adding eachzone of the first zone group to the second zone group.

In some embodiments, the detector is to monitor the user interface for adrag of a second icon representative of a first zone of the first zonegroup on the user interface from a third position to a fourth position.

In some embodiments, the configuration implementer is to change theconfiguration of the one or more zone groups by, when the fourthposition corresponds to a second one of the zone groups, adding thefirst the first zone to the second zone group.

In some embodiments, the configuration implementer is to change theconfiguration of the one or more zone groups by, when the fourthposition corresponds to an empty space, creating a new zone group thatincludes the first zone.

In some embodiments, the detector is to monitor the user interface for adrag of a second icon representative of a media item being playing inthe first zone group from a third position to a fourth position.

In some embodiments, the configuration implementer is to change theconfiguration of the one or more zone groups by, when the fourthposition corresponds to a second one of the zone groups, facilitating apresentation of the media item on a playback device associated with thesecond zone group.

An example method implemented in accordance with the present disclosureincludes monitoring a designated area of a user interface for a drag ofan icon representative of a first one of one or more zone groups on theuser interface from a first position to a second position, the one ormore zone groups each associated with one or more media playbackdevices; and changing a configuration of the one or more zone groups inresponse to a detected drag of the icon.

In some embodiments, changing the configuration of the one or more zonegroups comprises. when the second position corresponds to a second oneof the zone groups, adding each zone of the first zone group to thesecond zone group.

In some embodiments, the method further comprises monitoring the userinterface for a drag of a second icon representative of a first zone ofthe first zone group on the user interface from a third position to afourth position.

In some embodiments, changing the configuration of the one or more zonegroups comprises, when the fourth position corresponds to a second oneof the zone groups, adding the first the first zone to the second zonegroup.

In some embodiments, changing the configuration of the one or more zonegroups comprises, when the fourth position corresponds to an emptyspace, creating a new zone group that includes the first zone.

In some embodiments, the method further comprises monitoring the userinterface for a drag of a second icon representative of a media itembeing playing in the first zone group from a third position to a fourthposition.

In some embodiments, changing the configuration of the one or more zonegroups comprises, when the fourth position corresponds to a second oneof the zone groups, facilitating a presentation of the media item on aplayback device associated with the second zone group.

An example tangible machine-readable medium has instructions storedthereon implemented in accordance with the present disclosure that causea machine to at least monitor a designated area of a user interface fora drag of an icon representative of a first one of one or more zonegroups on the user interface from a first position to a second position,the one or more zone groups each associated with one or more mediaplayback devices; and change a configuration of the one or more zonegroups in response to a detected drag of the icon.

In some embodiments, the instructions are to cause the machine to changethe configuration of the one or more zones by, when the second positioncorresponds to a second one of the zone groups, adding each zone of thefirst zone group to the second zone group.

In some embodiments, the instructions are to cause the machine tomonitor the user interface for a drag of a second icon representative ofa first zone of the first zone group on the user interface from a thirdposition to a fourth position.

In some embodiments, the instructions are to cause the machine to changethe configuration of the one or more zone groups by, when the fourthposition corresponds to a second one of the zone groups, adding thefirst the first zone to the second zone group.

In some embodiments, the instructions are to cause the machine to changethe configuration of the one or more zone groups by, when the fourthposition corresponds to an empty space, creating a new zone group thatincludes the first zone.

In some embodiments, the instructions are to cause the machine tomonitor the user interface for a drag of a second icon representative ofa media item being playing in the first zone group from a third positionto a fourth position.

In some embodiments, the instructions are to cause the machine to changethe configuration of the one or more zone groups by, when the fourthposition corresponds to a second one of the zone groups, facilitating apresentation of the media item on a playback device associated with thesecond zone group.

Although the following discloses example methods, apparatus, systems,and articles of manufacture including, among other components, firmwareand/or software executed on hardware, it should be noted that suchmethods, apparatus, systems, and/or articles of manufacture are merelyillustrative and should not be considered as limiting. For example, itis contemplated that any or all of these firmware, hardware, and/orsoftware components could be embodied exclusively in hardware,exclusively in software, exclusively in firmware, or in any combinationof hardware, software, and/or firmware. Accordingly, while the followingdescribes example methods, apparatus, systems, and/or articles ofmanufacture, the examples provided are not the only way(s) to implementsuch methods, apparatus, systems, and/or articles of manufacture.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, etc., storing the software and/orfirmware.

These embodiments and many additional embodiments are described morebelow. Further, the detailed description is presented largely in termsof illustrative environments, systems, procedures, steps, logic blocks,processing, and other symbolic representations that directly orindirectly resemble the operations of data processing devices coupled tonetworks. These process descriptions and representations are typicallyused by those skilled in the art to most effectively convey thesubstance of their work to others skilled in the art. Numerous specificdetails are set forth to provide a thorough understanding of the presentdisclosure. However, it is understood to those skilled in the art thatcertain embodiments of the present disclosure may be practiced withoutcertain, specific details. In other instances, well known methods,procedures, components, and circuitry have not been described in detailto avoid unnecessarily obscuring aspects of the embodiments.

Reference herein to “embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentcan be included in at least one example embodiment of the invention. Theappearances of this phrase in various places in the specification arenot necessarily all referring to the same embodiment, nor are separateor alternative embodiments mutually exclusive of other embodiments. Assuch, the embodiments described herein, explicitly and implicitlyunderstood by one skilled in the art, may be combined with otherembodiments.

II. Example Environment

Referring now to the drawings, in which like numerals may refer to likeparts throughout the figures, FIG. 1 shows an example systemconfiguration 100 in which one or more of the method and/or apparatusdisclosed herein may be practiced or implemented. By way ofillustration, the system configuration 100 represents a home withmultiple zones. Each zone, for example, represents a different room orspace, such as an office, bathroom, bedroom, kitchen, dining room,family room, home theater room, utility or laundry room, and patio.While not shown here, a single zone may cover more than one room orspace. One or more of zone players 102-124 are shown in each respectivezone. A zone player 102-124, also referred to as a playback device,multimedia unit, speaker, etc., provides audio, video, and/oraudiovisual output. A controller 130 (e.g., shown in the kitchen forpurposes of illustration) provides control to the system configuration100. The system configuration 100 illustrates an example whole houseaudio system, though it is understood that the technology describedherein is not limited to its particular place of application or to anexpansive system like a whole house audio system 100 of FIG. 1.

FIGS. 2A, 2B, and 2C show example illustrations of zone players 200-204.The zone players 200-204 of FIGS. 2A, 2B, and 2C, respectively, maycorrespond to any of the zone players 102-124 of FIG. 1. While certainembodiments provide multiple zone players, an audio output may begenerated using only a single zone player. FIG. 2A illustrates a zoneplayer 200 including sound producing equipment 208 capable of generatingsound or an audio output corresponding to a signal received (e.g.,wirelessly and/or via a wired interface). The sound producing equipment208 of the zone player 200 of FIG. 2A includes a built-in amplifier (notshown in this illustration) and speakers (e.g., a tweeter, a mid-rangedriver, and/or a subwoofer. In certain embodiments, the zone player 200of FIG. 2A may be configured to play stereophonic audio or monauralaudio. As described in greater detail below, in some embodiments, theexample zone player 200 of FIG. 2A can also transmit a second signal to,for example, other zone player(s) in the same or different zone(s),speaker(s), receiver(s), etc. Transmission of the second signal may bepart of, for example, a system in which multiple zone players, speakers,receivers, etc. form a network to, for example, present media content ina synchronization or distributed manner.

The example zone player 202 of FIG. 2B includes a built-in amplifier(not shown in this illustration) to power a set of detached speakers210. The speakers 210 of FIG. 2B may include, for example, any type ofloudspeaker. The zone player 202 of FIG. 2B can communicate a signalcorresponding to audio content to the detached speakers 210 via wiredand/or wireless channels. Instead of receiving and generating audiocontent as in FIG. 2A, the zone player 202 of FIG. 2B receives the audiocontent and transmits the same (e.g., after processing the receivedsignal) to the detached speakers 210. Similar to the example zone player200 of FIG. 2A, in some embodiments the zone player 202 can transmit asecond signal to, for example, other zone player(s) in the same ordifferent zone(s), speaker(s), receiver(s), etc.

The example zone player 204 of FIG. 2C does not include an amplifier,but allows a receiver 214, or another audio and/or video type devicewith built-in amplification, to connect to a data network 128 of FIG. 1and to play audio received over the data network 128 via the receiver214 and a set of detached speakers 216. In addition to the wiredcouplings shown in FIG. 2C, the detached speakers 216 can receive audiocontent via a wireless communication channel between the detachedspeakers 216 and, for example, the zone player 204 and/or the receiver214. In some embodiments the zone player 202 can transmit a secondsignal to, for example, other zone player(s) in the same or differentzone(s), speaker(s), receiver(s), etc.

Example zone players include “Sonos® Play:3,” “Sonos Play:5,” “SonosConnect,” and “Sonos Connect:Amp,” which are offered by Sonos, Inc. ofSanta Barbara, Calif. A zone player may also be referred to herein as aplayback device, and a zone player is not limited to the particularexamples illustrated in FIGS. 2A, 2B, and 2C. For example, a zone playermay include a wired or wireless headphone. In another example, a zoneplayer might include a subwoofer. In an example, a zone player mayinclude or interact with a docking station for an Apple iPod™ or similardevice. In some embodiments, a zone player may relay one or more signalsreceived from, for example, a first zone player to another playbackdevice. In some embodiments, a zone player may receive a first signaland generate an output corresponding to the first signal and,simultaneously or separately, may receive a second signal and transmitor relay the second signal to another zone player(s), speaker(s),receiver(s), etc. Thus, an example zone player described herein can actas a playback device and, at the same time, operate as a hub in anetwork of zone players. In such instances, media content correspondingto the first signal may be different from the media contentcorresponding to the second signal.

FIG. 3 shows an example illustration of a wireless controller 300 in adocking station 302. The controller 300 may correspond to thecontrolling device 130 of FIG. 1. The controller 300 is provided with atouch screen 304 that allows a user to interact with the controller 300to, for example, retrieve and navigate a playlist of audio items,control operations of one or more zone players, and provide overallcontrol of the system configuration 100. In certain embodiments, anynumber of controllers may be used to control the system configuration100. In certain embodiments, there may be a limit on the number ofcontrollers that can control the system configuration 100. Thecontrollers might be wireless like wireless controller 300 or wired tothe data network 128. Furthermore, an application running on anynetwork-enabled portable devices, such as an iPhone™, iPad™, Android™powered phone, or any other smart phone or network-enabled device may beused as a controller by connecting to the data network 128. Anapplication running on a laptop or desktop PC or Mac may also be used asa controller. Example controllers include a “Sonos® Controller 200,”“Sonos® Controller for iPhone,” “Sonos® Controller for iPad,” “Sonos®Controller for Android, “Sonos® Controller for Mac or PC,” which areoffered by Sonos, Inc. of Santa Barbara, Calif. The flexibility of suchan application and its ability to be ported to a new type of portabledevice is advantageous.

Referring back to the system configuration 100 of FIG. 1, a particularzone may contain one or more zone players. For example, the family roomof FIG. 1 contains two zone players 106 and 108, while the kitchen isshown with one zone player 102. Zones may be dynamically configured bypositioning a zone player in a room or space and assigning via thecontroller 130 the zone player to a new or existing zone. As such, zonesmay be created, combined with another zone, removed, and given aspecific name (e.g., “Kitchen”), if so programmed. The zone players 102to 124 are coupled directly or indirectly to a data network, such as thedata network 128 shown in FIG. 1. The data network 128 is represented byan octagon in the figure to stand out from other components shown in thefigure. While the data network 128 is shown in a single location, it isunderstood that such a network may be distributed in and around thesystem configuration 100.

Particularly, the data network 128 may be a wired network, a wirelessnetwork, or a combination of both. In some embodiments, one or more ofthe zone players 102-124 are wirelessly coupled to the data network 128based on a proprietary mesh network. In some embodiments, one or more ofthe zone players 102-124 are wirelessly coupled to the data network 128using a non-mesh topology. In some embodiments, one or more of the zoneplayers 102-124 are coupled via a wire to the data network 128 usingEthernet or similar technology. In addition to the one or more zoneplayers 102-124 connecting to the data network 128, the data network 128may further allow access to a wide area network, such as the Internet.

In certain embodiments, the data network 128 may be created byconnecting any of the zone players 102-124, or some other connectingdevice, to a broadband router. Other zone players 102-124 may then beadded wired or wirelessly to the data network 128. For example, a zoneplayer (e.g., any of zone players 102-124) may be added to the systemconfiguration 100 by simply pressing a button on the zone player itself,which enables a connection to be made to the data network 128. Thebroadband router may be connected to an Internet Service Provider (ISP),for example. The broadband router may be used to form another datanetwork within the system configuration 100, which may be used in otherapplications (e.g., web surfing). The data network 128 may also be usedin other applications, if so programmed. Further, in certainembodiments, the data network 128 is the same network used for otherapplications in the household.

In certain embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows forsomeone to pass through zones while seamlessly listening to the audio.Further, zones may be put into a “party mode” such that all associatedzones will play audio in synchrony.

In certain embodiments, a zone contains two or more zone players. Forexample, the family room contains two zone players 106 and 108, and thehome theater room contains at least zone players 116, 118, and 120. Azone may be configured to contain as many zone players as desired, andfor example, the home theater room might contain additional zone playersto play audio from a 5.1 channel or greater audio source (e.g., a movieencoded with 5.1 or greater audio channels). If a zone contains two ormore zone players, such as the two zone players 106 and 108 in thefamily room, then the two zone players 106 and 108 may be configured toplay the same audio source in synchrony, or the two zone players 106 and108 may be paired to play two separate sounds in left and rightchannels, for example. In other words, the stereo effects of a sound maybe reproduced or enhanced through the two zone players 106 and 108, onefor the left sound and the other for the right sound. In certainembodiments, paired zone players may play audio in synchrony with otherzone players.

In certain embodiments, three or more zone players may be configured toplay various channels of audio that is encoded with three channels ormore sound. For example, the home theater room shows zone players 116,118, and 120. If the sound is encoded as 2.1 channel audio, then thezone player 116 may be configured to play left channel audio, the zoneplayer 118 may be configured to play right channel audio, and the zoneplayer 120 may be configured to play bass frequencies. Otherconfigurations are possible and depend on the number of zone players andthe type of audio. Further, a particular zone may be configured to playa 5.1 channel audio in one instance, such as when playing audio from amovie, and then dynamically switch to play stereo, such as when playingaudio from a two channel source.

In certain embodiments, two or more zone players may be sonicallyconsolidated to form a single, consolidated zone player. A consolidatedzone player (though made up of multiple, separate devices) may beconfigured to process and reproduce sound differently than anunconsolidated zone player or zone players that are paired, because aconsolidated zone player will have additional speaker drivers from whichsound may be passed. The consolidated zone player may further be pairedwith a single zone player or yet another consolidated zone player. Eachplayback device of a consolidated playback device is preferably set in aconsolidated mode.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

Sources of audio content to be played by zone players 102-124 arenumerous. Music from a personal library stored on a computer ornetworked-attached storage (NAS) may be accessed via the data network128 and played. Internet radio stations, shows, and podcasts may beaccessed via the data network 128. Music services that let a user streamand download music and audio content may be accessed via the datanetwork 128. Further, music may be obtained from traditional sources,such as a turntable or CD player, via a line-in connection to a zoneplayer, for example. Audio content may also be accessed through AirPlay™wireless technology by Apple, Inc., for example. Audio content receivedfrom one or more sources may be shared amongst the zone players 102 to124 via the data network 128 and/or the controller 130.

III. Example Playback Device

Referring now to FIG. 4, there is shown an example functional blockdiagram of a zone player 400 in accordance with an embodiment. The zoneplayer 400 of FIG. 4 includes a network interface 402, a processor 408,a memory 410, an audio processing component 412, a module 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 may beintegrated into another component. For example, the zone player 400could be constructed as part of a lamp for indoor or outdoor use.

Referring back to FIG. 4, the network interface 402 facilitates a dataflow between zone players and other devices on a data network (e.g., thedata network 128 of FIG. 1) and the zone player 400. In someembodiments, the network interface 402 may manage the assembling of anaudio source or file into smaller packets that are to be transmittedover the data network or reassembles received packets into the originalsource or file. In some embodiments, the network interface 402 mayfurther handle the address part of each packet so that it gets to theright destination or intercepts packets destined for the zone player400. Accordingly, in certain embodiments, each of the packets includesan Internet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, the network interface 402 may include one or bothof a wireless interface 404 and a wired interface 406. The wirelessinterface 404, also referred to as an RF interface, provides networkinterface functions for the zone player 400 to wirelessly communicatewith other devices (e.g., other zone player(s), speaker(s), receiver(s),component(s) associated with the data network 128, etc.) in accordancewith a communication protocol (e.g., any of the wireless standards IEEE802.11a, 802.11b, 802.11g, 802.11n, or 802.15). To receive wirelesssignals and to provide the wireless signals to the wireless interface404 and to transmit wireless signals, the zone player 400 of FIG. 4includes one or more antennas 420. The antenna(s) 420 are discussed ingreater detail below in connection with FIGS. 6A and 6B. The wiredinterface 406 provides network interface functions for the zone player400 to communicate over a wire with other devices in accordance with acommunication protocol (e.g., IEEE 802.3). In some embodiments, a zoneplayer includes both of the interfaces 404 and 406. In some embodiments,a zone player 400 includes only the wireless interface 404 or the wiredinterface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatmay be loaded with one or more software modules 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network. In someembodiments, a task might be for the zone player 400 to send audio datato another zone player or device on a network. In some embodiments, atask might be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmight be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks may be achieved via the one or more software modules 414 and theprocessor 408.

The audio processing component 412 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Incertain embodiments, the audio that is retrieved via the networkinterface 402 is processed and/or intentionally altered by the audioprocessing component 210. Further, the audio processing component 412may produce analog audio signals. The processed analog audio signals arethen provided to the audio amplifier 416 for play back through speakers418. In addition, the audio processing component 412 may includenecessary circuitry to process analog or digital signals as inputs toplay from zone player 400, send to another zone player on a network, orboth play and send to another zone player on the network. An exampleinput includes a line-in connection (e.g., an auto-detecting 3.5 mmaudio line-in connection).

The audio amplifier 416 is a device that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418may include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver may be a subwoofer (for low frequencies), amid-range driver (middle frequencies), and a tweeter (high frequencies),for example. An enclosure may be sealed or ported, for example.

A zone player 400 may also be referred to herein as a playback device.An example playback device includes a Sonos® S5, which is manufacturedby Sonos, Inc. of Santa Barbara, Calif. The S5 is an example zone playerwith a built-in amplifier and speakers. In particular, the S5 is afive-driver speaker system that includes two tweeters, two mid-rangedrivers, and one subwoofer. When playing audio content via the S5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies, just from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon may be played from a Sonos® S5. While the S5 is an example of a zoneplayer with speakers, it is understood that a zone player with speakersis not limited to one with a certain number of speakers (e.g., fivespeakers as in the S5), but rather can contain one or more speakers.Further, a zone player may be part of another device, which might evenserve a purpose different than audio (e.g., a lamp).

IV. Example Controller

Referring now to FIG. 5, there is shown an example controller 500, whichmay correspond to the controlling device 130 in FIG. 1. The controller500 may be used to facilitate the control of multi-media applications,automation and others in a system. In particular, the controller 500 isconfigured to facilitate a selection of a plurality of audio sourcesavailable on the network and enable control of one or more zone players(e.g., the zone players 102-124 in FIG. 1) through a wireless networkinterface 508. According to one embodiment, the wireless communicationis based on an industry standard (e.g., infrared, radio, wirelessstandards IEEE 802.11a, 802.11b 802.11g, 802.11n, or 802.15). Further,when a particular audio is being accessed via the controller 500 orbeing played via a zone player, a picture (e.g., album art) or any otherdata, associated with the audio source may be transmitted from a zoneplayer or other electronic device to the controller 500 for display.

The controller 500 is provided with a screen 502 and an input interface514 that allows a user to interact with the controller 500, for example,to navigate a playlist of many multimedia items and to controloperations of one or more zone players. The screen 502 on the controller500 may be an LCD screen or a touchscreen, for example. The screen 500communicates with and is commanded by a screen driver 504 that iscontrolled by a microcontroller (e.g., a processor) 506.

The controller 500 includes a network interface 508 that facilitateswireless communication with a zone player. In some embodiments, thecommands such as volume control and audio playback synchronization aresent via the network interface 508. In some embodiments, a saved zonegroup configuration is transmitted between a zone player and acontroller via the network interface 508. There may be more than onecontroller for a particular system. Further, a controller may beintegrated into a zone player.

In certain embodiments, a user may create a zone group including atleast two zone players from the controller 500. The zone players in thezone group may play audio in a synchronized fashion, such that all ofthe zone players in the zone group play back an identical audio sourceor a list of identical audio sources in a synchronized manner such thatno (or substantially no) audible delays or hiccups could be heard.Similarly, in some embodiments, when a user increases the audio volumeof the group from the controller 500, the signals or data of increasingthe audio volume for the group are sent to one of the zone players andcauses other zone players in the group to be increased together involume.

A user via the controller 500 may group zone players into a zone groupby activating a “Link Zones” soft button, or de-grouping a zone group byactivating an “Unlink Zones” or “Drop Zone” button. For example, onemechanism for ‘joining’ zone players together for audio play back is tolink a number of zone players together to form a group. To link a numberof zone players together, a user may manually link each zone player orroom one after the other. For example, assume that there is a multi-zonemedia playback system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of zone players(e.g., the zone players 102-124 of FIG. 1), for example, by startingwith a single zone and then manually linking each zone to that zone. Incertain embodiments, a set of zones can be dynamically linked togetherusing a command to create a zone scene or theme (subsequent to firstcreating the zone scene). For instance, a “Morning” zone scene commandmay link the Bedroom, Office, and Kitchen zones together in one action.Without this single command, the user would need to manually andindividually link each zone. The single command might include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed action. Other kinds of zone scenes may be programmed.

In certain embodiments, a zone scene may be triggered based on time(e.g., an alarm clock function). For instance, a zone scene may be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone may be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, etc.), a backup buzzer may be programmed to sound. Thebuzzer may include a sound file that is stored in a zone player, forexample.

The memory 510 may be loaded with one or more application modules 512that can be executed by the microcontroller 506 with or without a userinput via the user interface 514 to achieve certain tasks. In operation,when the microcontroller 506 executes one or more of the applicationmodules 512, the screen driver 504 generates control signals to drivethe screen 502 to display an application specific user interfaceaccordingly. In some embodiments, a first one of the applicationmodule(s) 512 is configured to facilitate grouping a number of selectedzone players into a zone group and synchronizing the zone players foraudio play back. In some embodiments, a second one of the applicationmodule(s) 512 is configured to control the audio sounds (e.g., volume)of the zone players in a zone group.

In the illustrated example of FIG. 5, the application module(s) 512include a zone manager 516 constructed in accordance with the teachingsof this disclosure. The example zone manager 516 manages a plurality ofzones, each corresponding to a set of playback devices (e.g., zoneplayers and/or speakers) defined to embody a respective zone. Theexample zone manager 516 is described in detail below in connection withFIGS. 6-14.

It should be noted that other network-enabled devices such as aniPhone®, iPad® or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac® may also be used as acontroller) may be used as a controller to interact or control zoneplayers in a particular environment. In such instances, the applicationmodule(s) 512, including the example zone manager 516, may beimplemented in connection with an application or program downloaded orotherwise executed by the network enabled device(s) (e.g., an iPhone®,iPad® or any other smart phone or network-enabled device). In someembodiments, a software application or upgrade may be downloaded onto anetwork enabled device to perform the functions disclosed herein.

V. Managing Zones of a Multi-Zone Media Playback System

An example apparatus that may be used to implement the example zonemanager 516 of FIG. 5 is illustrated in FIG. 6. Generally, the examplezone manager 516 of FIG. 6 enables a user of a touch screen interface toquickly and efficiently manage zones of a multi-zone media playbacksystem, such as the system 100 of FIG. 1. In particular, the zonemanager 516 detects certain interactions between a user of thecontroller 500 and a user interface implemented by the controller 500(e.g., an interface providing data to the input interface 514). Theexample zone manager 516 interprets the detected interactions andconfigures one or more aspects related to the zones of the multi-zonemedia playback system 100 accordingly. Unlike previous systems thatrequired the user to navigate to a screen or interface dedicated to aspecific zone to configure that zone, the example zone manager 516 ofFIGS. 5 and/or 6 enables the user to configure one or more zones from asingle screen or interface via simple gesture(s) (e.g., drag and drop).In other words, using the zone manager 516 of FIG. 5, the user canconfigure one or more zones from a single screen using simple gesturalcommands instead of having to navigate through a series of separatescreens each dedicated to a particular zone.

The example zone manager 516 of FIG. 6 includes a user interfacecommunicator 600. The user interface communicator 600 interacts with ormay be integrated with a user interface of the controller 500, such as auser interface providing input to the input interface 514 of FIG. 5. Theuser interface communicator 600 enables the zone manager 516 to receiveinformation regarding such inputs. Additionally or alternatively, theuser interface communicator 600 designates a portion of a display to bepresented on the screen 502 to be associated with the zone manager 516.In the illustrated example, the user interface communicator 600designates a Zone section of a user interface implemented by thecontroller 500 for an input that influences one or more configurationsof the multi-zone media playback system 100. FIG. 7 is a screenshot 700of an example user interface that may be implemented by the controller500 and/or into which the user interface communicator 600 of FIG. 6 maybe integrated. In the illustrated example, a Zone section 702 isdesignated to be associated with the example zone manager 516. The Zonesection 702 includes information related to the zones of the multi-zonemedia playback system 100 of FIG. 1. The example screenshot 700 of FIG.7 also includes a Now Playing section 704 that includes informationrelated to a media presentation (e.g., output of an audio track) beingpresented in a particular zone (e.g., the Living Room zone). The examplescreenshot 700 of FIG. 7 also includes a Media Source section 706, whichincludes a music library of media items available to the user of thecontroller 500. The library of the Media Source section 706 can includeone or more of a local library of media items, a non-local library ofmedia items, media items from a media service of a cloud, media itemslisting as search results from a query of the cloud service, and/or anyother suitable source of media items available to the controller 500.The example screenshot 700 of FIG. 7 also includes a Queue section 708,which reflects a list of media items to be presented by the devices(e.g., zone players and/or playback devices) in the zone shown in theNow Playing section 704, for example.

An isolated view of the Zone section 702 is shown in FIG. 8. The Zonesection 702 may be implemented into any aspect of the user interfaceimplemented by the controller 500 (e.g., as an overlay, adjacent theMedia Source section 706, etc.). The example Zone section 702 of FIG. 8includes a plurality of icons 800-810 representative of zone groups. Thezone group icons 800-810 may include a label to receive auser-selectable title. The example Zone section 702 also includes aninformation section 812 to indicate, for example, a current number ofgroups and a number of groups currently playing a media item. Theexample Zone section 702 also includes a now playing icon 814. In theillustrated example, the now playing icon 814 can be engaged to causethe Zone section 702 to change (e.g., flip) into one or more differentone(s) of the user interface sections shown in, for example FIG. 7(e.g., the Now Playing section 704 and/or the Queue section 708). Eachof the zone groups includes one or more zones of the system 100 of FIG.1 as selected by a user or administrator of the system 100. As describedabove, a zone may be defined to include one or more playback devices(e.g., zone players) located in one or more rooms of the system 100.Additionally, zones can be grouped to form zone groups. For example, afirst zone including two playback devices in a kitchen can be combinedwith a second zone including one playback device in a dining room toform a zone group including playback devices in the kitchen and diningroom. The resulting zone group can be grouped based on proximity of thekitchen to the dining room and/or a characteristic of the rooms or zones(e.g., eating areas). As described above, playback devices can be zonedand zones can be grouped according to any desire of the user. A firstone of the zone group icons 800 in the example of FIG. 8 represents afirst zone group including a kitchen zone and a dining room zone. In thefirst zone group icon 800, a first zone icon 816 is placed adjacent alabel corresponding to the kitchen zone and a second zone icon 818 isplaced adjacent a label corresponding to the dining room zone. Further,the first zone group icon 800 includes a now playing status bar 820indicative of a media item (e.g., a song) being presented by theplayback devices of the first zone group. Interactions and responses tothe interactions related to the elements of the Zone section 702 tomanage the zones and/or zone groups of the system are described indetail below.

Referring back to FIG. 6, the user interface communicator 600 receivesinformation related to interactions between a user and the Now Playingsection 702 and provides the received information to a drag detector602, a tap detector 604, an element identifier 606, and a destinationidentifier 608. The drag detector 602 interprets information receivedvia the user interface communicator 600 to determine whether the userhas dragged an icon across the display using, for example, the touchscreen implementing the display or a cursor that has selected a displayelement. For example, the drag detector 602 may determine if acontinuous line or streak of inputs occurred across a touch screen.Additionally or alternatively, the drag detector 602 may determine thata cursor has selected an element and has been dragged across a userinterface. Similarly, the tap detector 604 interprets informationreceived via the user interface communicator 600 to determine whetherthe user has tapped an icon using, for example, the touch screenimplementing the display or a button associated with a cursor. Forexample, the tap detector 604 may determine whether a designated shape(e.g., a button of a mouse or a finger) engaged the screen for adesignated period of time (e.g., two tenths of a second). Such inputs(e.g., drags and taps) are understood by the user (e.g., as explained ina user manual) to manage the zones and/or zone groups of the Zonesection 702 in one or more manners.

The element identifier 606 also interprets information received via theuser interface communicator 600 to identify which element (e.g., icon)of the Zone section 702 corresponds to a detected drag and/or tap. Forexample, the element identifier 606 may determine a coordinate of adetected drag or tap on the display and use the coordinate to referencea database including mappings of the elements of the Zone section 702.That is, by detecting a location of an interaction with one of theelements (e.g., icons) and determining which element is currentdisplayed at that location, the element identifier 606 identifies theelement with which the interaction (detected by the drag detector 602 orthe tap detector 604) occurred.

The destination identifier 608 also interprets information received viathe user interface communicator 600 to identify a location on thedisplay at which a dragged element is dropped or stops being dragged.For example, the destination identifier 608 may determine a location atwhich a detected drag is no longer providing input to the user interfaceafter providing input continuously across the user interface. Elementscan be dragged and dropped on any suitable area of the displayincluding, for example, on top of other display elements or unoccupiedspace of the display.

Together, the drag detector 602, the tap detector 604, the elementidentifier 606, and the destination identifier 608 are able to determinethe intention of the user behind the detected and analyzed interactionwith the touch screen. Certain interactions are defined in to result in,for example, configuration (or reconfiguration) of the zone groups,configuration of the display or user interface, presentation of mediaitem(s) in one or more zones and/or zone groups, etc. The interactionsdefined by the zone manager 516 to configure the zones of the system 100are provided to a user of the controller 500 using, for example, a usermanual or a help interface implemented on the controller 500 and/or in aseparately provided publication (e.g., a booklet o dedicated web page).Moreover, the definitions associated with the configuration of the zonesusing the zone manager 516 are stored in an instructions database 610.Thus, the instructions database 610 includes a plurality of entries,each corresponding to a detected interaction with the touch screen ofthe controller 500. One or more configuration instructions are stored inconnection with each entry of the instructions database 610. Theinstructions database 610 can be referenced or queried with a certaininteraction detected on the controller 500 and will returninstruction(s) regarding how the zone(s), zone group(s), playbackdevice(s), etc. are to be configured (or reconfigured). The definitionsof the instructions database 610 are supplied by any suitable source(e.g., a designer or manufacturer of the controller 500, a provider ofthe system 100 of FIG. 1, a designer or manufacturer of the playbackdevices, etc.) and may be customizable and/or adjustable by any suitableparty (e.g., a user of the system 100 or the controller 500, a providerof the system 100, a provider of the playback devices, etc.).

The example zone manager 516 of FIG. 6 includes a zone configurationimplementer 612 to carry out the configuration instructions of theinstructions database 610. In the illustrated example, the implementer612 receives data from one or more of the drag detector 602, the tapdetector 604, the element identifier 606, and the destination identifier608. Using the received data, the implementer 612 references theinstructions database 610 to determine how, if at all, the zone(s), zonegroup(s), playback device(s), etc. are to be configured (orreconfigured). The implementer 612 then facilitates any changes inaccordance with the instructions of the database 610. For example, theimplementer 612 may work with the user interface communicator 600 tochange one or more aspects or settings of the display. Additionally oralternatively, the implementer 612 may work with an interface (e.g., thenetwork interface 508) to communicate instructions to one or moreplayback devices to output a media item. Additionally or alternatively,the implementer 612 may change one or more zone group definitions suchthat a new zone group is added to the system 100, a zone is moved fromone zone group to another, a zone is copied into a second zone group, azone is eliminated from a zone group, etc. These and otherconfigurations of the system 100 and/or the controller 500 areimplemented by the configuration implementer 612 as described below inconnection with FIGS. 9-13.

FIG. 9 is a screenshot illustrating example interactions that may bedetected and processed by the example zone manager 516 of FIG. 6 inconnection with the Zone section 702 of FIGS. 7 and/or 8. In particular,the tap detector 604 can detect a tap in a location of the screenshot900 corresponding to the now playing icon 814. In such instances, theelement identifier 606 determines that the tapped location correspondsto the now playing icon 814. In response to receiving data indicative ofthe tap of the now playing icon 814, the implementer 612 references theinstructions database 610. In accordance with the correspondinginstructions of the database 610, the implementer 612 causes the screendriver 504, for example, to alter the display on the screen 502. In theillustrated example, the alteration of the display includes the Zonesection 702 being flipped to reveal the Now Playing section 704 or theQueue section 708 in the space previously occupied by the Zone section702.

Additionally, the tap detector 604 can detect a tap in a location of thescreenshot 900 corresponding to the now playing status bar 820. Asdescried above, the now playing status bar 820 is indicative of a mediaitem (e.g., a song) being presented by the playback device(s) of thezone group corresponding to the icon in which the now playing status bar820 is displayed. In the illustrated example of FIG. 9, the elementidentifier 606 determines that the tapped location corresponds to thenow playing status bar 820 of the first zone group icon 800. In responseto receiving data indicative of a tap of the now playing status bar 820associated with the first zone group icon 800, the implementer 612references the instructions database 610. In accordance with thecorresponding instructions of the database 610, the implementer 612causes the controller 500 (e.g., via the micro controller 506) to togglethe corresponding media item from playing or pausing/stop. That is, ifthe media item was being presented before the detected tap of the nowplaying status bar 820, the media item is paused or stopped. On theother hand, if the media item was paused or stopped before the detectedtap of the now playing status bar 820, the media item is played inconnection with the zone group being represented by the first zone groupicon 800.

Additionally, the tap detector 604 can detect a tap in a location of thescreenshot 900 corresponding to one of the zone icons. In theillustrated example of FIG. 9, the element identifier 606 determinesthat the tapped location corresponds to the zone icon 818 representingthe dining room zone. In response to receiving data indicative of a tapof the zone icon 818 of the first zone group icon 800, the implementer612 references the instructions database 610. In accordance with thecorresponding instructions of the database 610, the implementer 612causes the controller 500 (e.g., via the micro controller 506) to togglethe volume level of the corresponding zone (e.g, the dining room zone)between a mute and non-mute state. In such instances, the zone group inwhich the zone icon is placed is not selected as a current zone.Instead, the operation of the zone associated with the icon is altereddirectly. That is, the example zone manager 516 enables the user to mutea zone with having to navigate to a screen or interface dedicated solelyto the dining zone. The implementer 612 can also cause the screen 502 todisplay a mute graphic or a no-mute graphic proximate the zone when thetap detector 604 detects a change, for example.

Additionally, the tap detector 604 can detect a tap in a location of thescreenshot 900 corresponding to one of the zone group icons. In theillustrated example of FIG. 9, the element identifier 606 determinesthat the tapped location corresponds to the second zone group icon 802representing the second zone group (which includes a living room zone).In response to receiving data indicative of a tap of the second zonegroup icon 802, the implementer 612 references the instructions database610. In accordance with the corresponding instructions of the database610, the implementer 612 causes the controller 500 (e.g., via the microcontroller 506) to select the second zone group as the current zonegroup. Such a selection of a zone group as the current zone group causesother aspects of the controller to control the selected zone group. Forexample, a Control section 710 of FIG. 7 will control playback devicesof the selected zone group. Further, the implementer 612 can also causethe screen 502 to highlight the selected current zone group in responseto the detected tapping of that zone group.

Additionally, the tap detector 604 can detect a tap in a location of thescreenshot 900 corresponding to a ‘plus’ icon 902 in one of the zonegroup icons 800-812. In the illustrated example of FIG. 9, the elementidentifier 606 determines that the tapped location corresponds to a‘plus’ icon 902 in the sixth zone group icon 810. In response toreceiving data indicative of a tap of the ‘plus’ icon 902, theimplementer 612 reference the instructions of the database 610. Inaccordance with the corresponding instructions of the database 610, theimplementer 612 causes the screen driver 504 to cause the display of thescreen 502 to expand the sixth zone group icon 810 to reveal additionalzones in the sixth zone group. While the screenshot 900 shows only apatio zone being listed in the sixth zone group icon 810, the ‘plus’icon 902 indicates that the sixth zone group has more zones than arelisted. Tapping of the ‘plus’ icon 902 causes the sixth zone group icon810 to extend vertically to reveal the additional zones. In someexamples, the expanded version of the sixth zone group icon 810 may havea ‘minus’ icon in lieu of the ‘plus’ icon 902,’ the selection of whichcause the sixth zone group icon 810 to retract to again only reveal asubset of the zones of the sixth zone group.

Additionally, the drag detector 604 can detect a drag of a displayelement across the screenshot 900. In some examples, the drag detector604 detects a drag of one of the zone group icons 800-812. An exampledrag is shown in FIG. 9 by an arrow 904. In particular, a user hasdragged the now playing status bar 820 of the first zone group icon 800,which represents the currently played stream of media in the first zonegroup playback device(s). The example element identifier 606 identifiesthe now playing status bar 820 as the element being dragged. Further,the destination identifier 608 identifies a location at which thedragged element is dropped (e.g., where the detected drag ended). In theexample of FIG. 9, the destination identifier 608 identifies a fifthzone group icon 808 as the destination of the dragged now playing statusbar 820. In response to receiving data indicative of a drag of the nowplaying status bar 820 to the fifth zone group icon 808, the implementer612 references the instructions of the database 610. In accordance withthe corresponding instructions of the database 610, the implementer 612causes the controller 500 to instruct the playback devices of the fifthzone group to output the media stream corresponding to the dragged nowplaying status bar 820. That is, the implementer 612 causes the mediabeing output at the time of the detected drag to be output in the zonegroup corresponding to the destination of the drag. In some examples,the media steam may cease in the zone group from which the drag occurred(e.g., the first zone group in the example of FIG. 9). In some examples,the media stream continues to play in the zone group from which the dragoccurred. In some examples, a queue associated with the dragged mediastream is also transferred to the destination zone group and thedestination zone group continues to play the queue media items. Thus,the fifth zone group 808 seamlessly picks up the media stream that wasdragged from the first zone group 800 to the fifth zone group 808 viathe now playing status bar 820.

FIG. 10 is a screenshot 1000 of the example Zone section 702illustrating an example interaction that may be detected and processedby the example zone manager 516 of FIGS. 5 and/or 6. In particular, thedrag detector 604 detects a drag of the sixth zone group icon 810 up thelist of zone group icons 800-810. Such a drag is shown in FIG. 10 by anarrow 1002. The example element identifier 606 identifies the sixth zonegroup icon 810 as the element being dragged. Further, the destinationidentifier 608 identifies a location at which the dragged element isdropped (e.g., where the detected drag ended). In the example of FIG.10, the destination identifier 608 identifies a space between the thirdzone group icon 804 and the fourth zone group icon 806 as thedestination of the dragged sixth zone group icon 810. In response toreceiving data indicative of a drag of the sixth zone group icon 810,the implementer 612 references the instructions of the database 610. Inaccordance with the corresponding instructions of the database 610, theimplementer 612 causes the screen driver 504 to alter the display on thescreen 502 such that the zone group icons are reordered to insert thesixth zone group icon between the third and fourth icons 804 and 806,respectively. In the illustrated example, a drop zone target line 1004appears as the element (e.g., the icon 810) is dragged among the zonegroup icons.

FIG. 11 is a screenshot 1100 of the example Zone section 702illustrating an example interaction that may be detected and processedby the example zone manager 516 of FIGS. 5 and/or 6. In particular, thedrag detector 604 detects a drag of the sixth zone group icon 810 up thelist of zone group icons 800-810. Such a drag is shown in FIG. 11 by anarrow 1102. The example element identifier 606 identifies the sixth zonegroup icon 810 as the element being dragged. Further, the destinationidentifier 608 identifies a location at which the dragged element isdropped (e.g., where the detected drag ended). In the example of FIG.11, the destination identifier 608 identifies one of the other zonegroup icons as the destination of the dragged sixth zone group icon 810.In the illustrated example, the sixth zone group icon 810 is draggedonto the first zone group icon 800. In response to receiving dataindicative of a drag of the sixth zone group icon 810 onto the firstzone group icon 800, the implementer 612 references the instructions ofthe database 610. In accordance with the corresponding instructions ofthe database 610, the implementer 612 causes the controller 500 (e.g.,via the micro controller 506) to add the zones of the sixth zone groupto the first zone group. For example, the implementer 612 causes thescreen driver 504 to alter the display on the screen 502 such that thezones of the sixth zone group are listed in the first zone group icon800. Further, a list maintaining the configurations of the zone groups(e.g., a memory tracking the assignments of zones to zone groups) isupdated to reflect the new members of the first zone group. In someexamples, the zone group icons onto which the dragged element is draggedover are highlighted to indicate a drop target if the element is droppedat a corresponding location.

FIG. 12 is a screenshot 1200 of the example Zone section 702illustrating an example interaction that may be detected and processedby the example zone manager 516 of FIGS. 5 and/or 6. In particular, thedrag detector 604 detects a drag of a zone icon of a zone group icon toanother zone group icon. One such example drag is shown in FIG. 12 by afirst arrow 1202. In particular, the example element identifier 606identifies the zone icon 816 corresponding to the kitchen zone as beingdragged. Further, the destination identifier 608 identifies the secondzone group icon 802 as the destination of the dragged zone icon 816 (asshown by the first arrow 1202). In response to receiving data indicativeof a drag of the zone icon 816 onto the second zone group icon 802, theimplementer 612 references the instructions of the database 610. Inaccordance with the corresponding instructions of the database 610, theimplementer 612 causes the controller 500 (e.g., via the microcontroller 506) to add the zone corresponding to the dragged zone icon816 (e.g., the kitchen zone) the second zone group. For example, theimplementer 612 causes the screen driver 504 to alter the display on thescreen 502 such that the kitchen zone is listed in the second zone groupicon 802. Further, a list maintaining the configurations of the zonegroups (e.g., a memory tracking the assignments of zones to zone groups)is updated to reflect the new member of the second zone group. In someexamples, the zone group icons onto which the dragged element is draggedover are highlighted to indicate a drop target if the element is droppedat a corresponding location.

Another drag of the zone icon 816 is shown in FIG. 12 by a second arrow1204. In particular, the example element identifier 606 identifies thezone icon 816 corresponding to the kitchen zone as being dragged.Further, the destination identifier 608 identifies a space 1206 betweenthe third zone group icon 804 and the fourth zone group icon 806 as thedestination of the dragged zone icon 816. In response to receiving dataindicative of a drag of the zone icon 816, the implementer 612references the instructions of the database 610. In accordance with thecorresponding instructions of the database 610, the implementer 612causes the screen driver 504 to alter the display on the screen 502 suchthat a new zone group is displayed at the identified destination.Further, a list maintaining the configurations of the zone groups (e.g.,a memory tracking the assignments of zones to zone groups) is updated toreflect the new zone group. The new zone group includes the zonecorresponding to the dragged zone icon 816. In some examples, the zoneis removed from the first zone group.

FIG. 13 is a screenshot 1300 of the example Zone section 702 and theexample Music Source section 706 illustrating an example interactionthat may be detected and processed by the example zone manager 516 ofFIGS. 5 and/or 6. In particular, the drag detector 604 detects a drag ofa media item 1302 from the Music Source section 706 to a zone groupicon. Such a drag is shown in FIG. 13 by an arrow 1304. In particular,the example element identifier 606 identifies the media item 1302 as theelement being dragged. The media item 1302 represents, for example, asong, a playlist of songs, a streaming channel, a station, etc. Thedestination identifier 608 identifies the third zone group icon 804 asthe destination of the dragged media item 1302 (as shown by the arrow1304). In response to receiving data indicative of a drag of the mediaitem 1302 onto the third zone group icon 804, the implementer 612references the instructions of the database 610. In accordance with thecorresponding instructions of the database 610, the implementer 612causes the controller 500 (e.g., via the micro controller 506) instructthe playback device(s) of the third zone group to play the media contentcorresponding to the media item 1302. The implementer 612 may also causethe screen driver 504 to alter the display on the screen 502 such thatdata representative of the media item 1302 is presented in the nowplaying status bar of the third zone group icon 804. In some examples,the drag described above in connection with the arrow 1304 does notchange the current zone group, as the second zone group remains thecurrently selected zone group (e.g., as indicated by the highlighting ofthe second zone group icon 802).

FIG. 14 is a flow diagram representative of example machine readableinstructions that may be executed to implement the example zone manager516 of FIGS. 5 and/or 6. The example of FIG. 14 begins with the userinterface communicator 600 receiving an input from the screen 502 of thecontroller 500 (block 1400). The components of the example zone manager516 analyze the received input to determine a type of the input, anelement associated with the input, and a destination associated with theinput (if any). In the illustrated example, the tap detector 604determines whether the input corresponds to a user tapping the screen502 (which may be implemented by a touch screen and/or a screenincluding a cursor) (block 1402). If the input corresponds to a tapcontrol passes to block 1408. If the input does not correspond to a tap,the drag detector 602 determines whether the input corresponds to a dragof a display element (block 1404). If the input does not correspond to adrag at block 1404, the example of FIG. 14 ends (block 1414). If theinput does corresponds to a drag of a display element, the destinationidentifier 608 determines a location on the user interface at which thedragged display element was dropped (block 1406).

The element identifier 606 then identifies which of the display elementswas dragged or tapped (block 1408). The instructions database 1610 isthen queried with the information gathered by the drag detector 602, thetap detector 604, the element identifier 606, and/or the destinationidentifier 608 to determine one or more actions to take in connectionwith the system 100 in response to the received input (block 1410). Thedatabase 1610 then provides the appropriate instructions to the zoneconfiguration implementer 1612, which implements the correspondingconfiguration (or reconfiguration) of the zones of the system 100 (block1412). Example configurations are demonstrated above in connection withFIGS. 7-13. The example of FIG. 9 then ends (block 1414).

Various inventions have been described in sufficient detail with acertain degree of particularity. It is understood to those skilled inthe art that the present disclosure of embodiments has been made by wayof examples only and that numerous changes in the arrangement andcombination of parts may be resorted without departing from the spiritand scope of the present disclosure as claimed. While the embodimentsdiscussed herein may appear to include some limitations as to thepresentation of the information units, in terms of the format andarrangement, the embodiments have applicability well beyond suchembodiment, which can be appreciated by those skilled in the art.Accordingly, the scope of the present disclosure is defined by theappended claims rather than the forgoing description of embodiments.

We claim:
 1. An apparatus including a processor, the apparatusconfigured to: display a first zone group display region including afirst status icon and a first zone icon identifying at least one firstzone player, the first status icon representative of a first playbackstatus of a first zone group; display a second zone group display regionincluding a second status icon and a second zone icon identifying atleast one second zone player, the second status icon representative of asecond playback status of a second zone group; and in response to afirst drag of the first zone icon from a first position to a secondposition inside the second zone group display region: cause the at leastone first zone player to join the second zone group with the at leastone second zone player; cause the first zone icon to be displayed in thesecond zone group display region; and cause the at least one first zoneplayer to adopt the second playback status of the second zone group. 2.The apparatus as defined in claim 1, wherein the apparatus is furtherconfigured to change the second playback status of the second zone groupin response to a second drag of the first status icon inside the secondzone group display region.
 3. The apparatus as defined in claim 2,wherein changing of the second playback status comprises causing thesecond playback status to correspond to the first playback status. 4.The apparatus as defined in claim 2, wherein changing of the secondplayback status comprises causing the at least one second zone player topresent media being presented by the at least one first zone player. 5.The apparatus as defined in claim 1, wherein the apparatus is furtherconfigured to monitor a user interface including the first and secondzone group display regions for a drag input.
 6. The apparatus as definedin claim 1, wherein the first status icon is indicative of a song beingplayed by the at least one first zone player.
 7. The apparatus asdefined in claim 1, wherein: the first playback status indicates firstmedia being played in the first zone group; the second playback statusindicates second media being played in the second zone group; and theapparatus is further configured to cause the at least one first zoneplayer to play the second media in response to the first drag.
 8. Amethod, comprising: displaying, via a controller device, a first zonegroup display region including a first status icon and a first zone iconidentifying at least one first zone player, the first status iconrepresentative of a first playback status of a first zone group;displaying, via the controller device, a second zone group displayregion including a second status icon and a second zone icon identifyingat least one second zone player, the second status icon representativeof a second playback status of a second zone group; and in response to afirst drag of the first zone icon from a first position to a secondposition inside the second zone group display region: causing, via thecontroller device, the at least one first zone player to join the atleast one second zone player in the second zone group; causing, via thecontroller device, the first zone icon to be displayed in the secondzone group display region; and causing, via the controller device, theat least one first zone player to adopt the second playback status ofthe second zone group.
 9. The method as defined in claim 8, furthercomprising changing the second playback status of the second zone groupin response to a second drag of the first status icon inside the secondzone group display region.
 10. The method as defined in claim 9, whereinthe changing of the second playback status comprises causing the secondplayback status to correspond to the first playback status.
 11. Themethod as defined in claim 9, wherein the changing of the secondplayback status comprises causing the at least one second zone player topresent media being presented by the at least one first zone player. 12.The method as defined in claim 8, further comprising monitoring a userinterface including the first and second zone group display regions fora drag input.
 13. The method as defined in claim 8, wherein the firststatus icon is indicative of a song being played by the at least onefirst zone player.
 14. The method as defined in claim 8, wherein: thefirst playback status indicates first media being played in the firstzone group; the second playback status indicates second media beingplayed in the second zone group; and wherein the method furthercomprises causing the at least one first zone player to play the secondmedia in response to the first drag.
 15. A tangible, non-transitorycomputer-readable storage medium including instructions that, whenexecuted, cause a computing device to perform a method comprising:displaying a first zone group display region including a first statusicon and a first zone icon identifying at least one first zone player,the first status icon representative of a first playback status of afirst zone group; displaying a second zone group display regionincluding a second status icon and a second zone icon identifying atleast one second zone player, the second status icon representative of asecond playback status of a second zone group; and in response to afirst drag of the first zone icon from a first position to a secondposition inside the second zone group display region: causing the atleast one first zone player to join the at least one second zone playerin the second zone group; causing the first zone icon to be displayed inthe second zone group display region; and causing the at least one firstzone player to adopt the second playback status of the second zonegroup.
 16. The tangible, non-transitory computer-readable storage mediumof claim 15, wherein the method further comprises changing the secondplayback status of the second zone group in response to a second drag ofthe first status icon inside the second zone group display region. 17.The tangible, non-transitory computer-readable storage medium of claim16, wherein the changing of the second playback status comprises causingthe second playback status to correspond to the first playback status.18. The tangible, non-transitory computer-readable storage medium ofclaim 16, wherein the changing of the second playback status comprisescausing the second zone player to present media being presented by thefirst zone player.
 19. The tangible, non-transitory computer-readablemedium of claim 15, wherein the method further comprises monitoring auser interface including the first and second zone group display regionsfor a drag input.
 20. The tangible, non-transitory computer-readablestorage medium of claim 15, wherein the first status icon is indicativeof a song being played by the at least one first zone player.
 21. Thetangible, non-transitory computer-readable storage medium of claim 15,wherein: the first playback status indicates first media being played inthe first zone group; the second playback status indicates second mediabeing played in the second zone group; and wherein the method furthercomprises causing the at least one first zone player to play the secondmedia in response to the first drag.